Integrating a mobile hotspot into a larger network environment

ABSTRACT

Integration of a mobile hotspot into a service provider network is disclosed. A network node establishes a first wireless communication link with a mobile hotspot device. The mobile hotspot device is configured to establish a second wireless communications link with at least one client device. The network node receives an access request message from the mobile hotspot device which comprises credentials provided by the at least one client device. The network node determines that the at least one client device is authorized to access the service provider network through the mobile hotspot device based on the credentials and indicates to the mobile hotspot device that the at least one client device is authorized to access the service provider network through the mobile hotspot device.

RELATED APPLICATIONS

This application claims the benefit of provisional patent applicationSer. No. 61/599,081, filed Feb. 15, 2012, the disclosure of which ishereby incorporated herein by reference in its entirety.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to wireless access of anetwork, and in particular to the integration of a mobile hotspot deviceinto a larger network environment.

BACKGROUND

New “4G” cellular data technologies such as WiMax and LTE makehigh-bandwidth applications, such as streaming video applications,possible. Such applications have driven the demand for data byconsumers. Wireless service providers are making significant investmentsin their infrastructure to meet this demand. Because wirelesssubscription fees are extremely competitive, service differentiators areincreasingly important to maintain existing subscribers and attract newones. Moreover, data usage instead of voice communications is drivingrevenue for service providers, so service providers are incented to findways to increase demand for data by its subscribers.

Many mobile devices today include a wireless interface such as a Wi-Fiinterface that allows the mobile device to connect to a wireless localarea network and access the Internet. Some of these mobile devices, suchas cellular phone mobile devices, also include a cellular interface thatallows the mobile device to access the Internet via a cellularcommunication link even when not in the presence of a wireless localarea network, such as when in a vehicle. Such devices increasingly alsohave hotspot functionality that allows the mobile device to serve as amobile hotspot, such that other Wi-Fi capable devices, referred toherein as client devices, may connect to the mobile device via the Wi-Fiinterface, and access the Internet via the mobile device's cellularcommunication link. In this role the mobile device serves essentially asa wireless access point and router for client devices that would nototherwise have access to the Internet.

A service provider creates a potential new portal to their network eachtime one of their subscribers' devices with hotspot functionality iswithin wireless range of the service provider network. Since cellularphones increasingly have such functionality, it would be beneficial if aservice provider could leverage its subscribers' devices to offerInternet access (and facilitate corresponding data usage) to otherdevices that are in Wi-Fi proximity of the cellular device, in a mannerthat benefits the service provider, as well as its subscribers.

SUMMARY

The present disclosure discloses mechanisms for facilitating access to aservice provider network by integrating mobile subscriber devices intothe service provider network, and thereby extending the reach of theservice provider network to any location that a subscriber's device isenabled. In one embodiment, the subscriber's device, sometimes referredto herein as a mobile hotspot device (MHD), may be configured, orprovisioned, automatically by the service provider with a wireless localarea network (LAN) having a predetermined name, such as a predeterminedservice set identifier (SSID). The MHD may periodically broadcast theSSID to any other devices, sometimes referred to herein as clientdevices, which may be in wireless range of the MHD. Certain clientdevices may be programmed to detect the predetermined SSID, and inresponse, attempt to establish communication with the service providernetwork via the MHD.

In one embodiment, the client device may communicate credentials to theMHD. The MHD generates an access request message that includes thecredentials, and sends the access request message to the serviceprovider network for authentication. A network node in the serviceprovider network receives the access request message, determines thatthe client device is authorized to access the service provider networkthrough the MHD based on the credentials, and indicates to the MHD thatthe client device is so authorized.

In one embodiment, authorization may in part be based on whether a userof the client device has a subscription to access the service providernetwork. For example, the client device may comprise a cellular phonethat receives service via the service provider network in accordancewith the subscription with the service provider. The client device mayhave Wi-Fi capability, but not cellular data capability. The clientdevice may include a client application that detects broadcasted SSIDs,and upon detecting an SSID that is the predetermined SSID, such as thehotspot offered by the MHD, recognize the hotspot as a service providerwireless LAN, and initiate the authorization sequence mentioned aboveautomatically. Once authorized, the user of the client device enjoysInternet access that may not otherwise be obtainable at that particularlocation. In another embodiment, the client device may comprise a Wi-Ficapable laptop computer or tablet computer of a subscriber of theservice provider. The client device includes the client application aswell as suitable credentials that identify the device as beingassociated with the subscriber.

In one embodiment, the MHD is a cellular phone that enjoys access to theservice provider network by virtue of a subscription between an owner ofthe MHD and the service provider. The MHD may concurrently provide bothvoice service to the owner, as well as mobile hotspot functionality suchas data communications between the Internet and one or more clientdevices. Data usage by each client device may be counted against thesubscription associated with the respective client device, rather thanthe MHD, so that the owner of the MHD is not penalized for providingaccess to the service provider network. Data usage by client devicesthat are associated with the subscription of the MHD, such as familymembers' client devices, may be counted against the subscription of theMHD. In one embodiment, the network node may determine that a clientdevice has exceeded an allotment, such as a monthly allotment,associated with the client device subscription, and de-authorize accessby the client device to the service provider network.

Prioritization of requests for data may be based on the client device towhich the data is destined. In particular, data requested by the MHD mayenjoy a higher priority than data requested by a client device. In thismanner, the owner of the MHD is not penalized for allowing the MHD to beused as a mobile hotspot. For example, if the owner of the MHD initiatesa first request for a first streaming movie from an Internet movieservice, and a user of a client device similarly initiates a secondrequest for a second streaming movie from an Internet movie service,sufficient bandwidth may be reserved for the first streaming movie sothat the first streaming movie is provided at a relatively highresolution. Remaining bandwidth may be insufficient to provide thesecond streaming movie, or may require that a lower resolution versionbe provided to the client device. Such prioritization mechanisms may beimplemented by the network node, the MHD, or a combination of both.

In one embodiment, upon receipt of a connection request by a clientdevice, the MHD may access configuration data maintained on the MHD thatidentifies permitted client devices. For example, the owner of the MHDmay identify family members' and particular associates', friends' orcolleagues' client devices as being permitted client devices. If theclient device is not identified in the configuration data as a permittedclient device, the MHD does not generate and send an access requestmessage with the client device's credentials to the network node,effectively barring access to the service provider network by the clientdevice.

In one embodiment, the owner of the MHD may be compensated by theservice provider for allowing the MHD to be used as a portal to theservice provider network. For example, the service provider may reduce aportion of the monthly subscription fee of the owner based on thequantity of data that travels through the MHD on a path to a clientdevice. Alternatively or additionally, the service provider may increasea data usage allotment associated with the MHD such that the MHD enjoysa larger data usage allotment based on the quantity of data that travelsthrough the MHD on a path to a client device. Those of skill in the artwill recognize that other compensation mechanisms are possible.

Those skilled in the art will appreciate the scope of the presentdisclosure and realize additional aspects thereof after reading thefollowing detailed description of the preferred embodiments inassociation with the accompanying drawing figures.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

The accompanying drawing figures incorporated in and forming a part ofthis specification illustrate several aspects of the disclosure, andtogether with the description serve to explain the principles of thedisclosure.

FIG. 1 is a block diagram illustrating a system in which embodiments ofthe present disclosure may be practiced;

FIG. 2 is a block diagram of the system illustrated in FIG. 1 showinggreater detail of certain components;

FIG. 3 illustrates an exemplary message flow for facilitating access toa service provider network by a client device via a mobile hotspotdevice (MHD);

FIG. 4 is a block diagram of the system illustrated in FIG. 1 accordingto another embodiment;

FIG. 5 illustrates an exemplary message flow for providing voice signalsand data destined for different devices to the MHD concurrently;

FIG. 6 illustrates an exemplary message flow for accounting for datausage by devices that receive data via the service provider networkaccording to one embodiment;

FIG. 7 illustrates another exemplary message flow for accounting fordata usage by devices that receive data via the service provider networkaccording to another embodiment;

FIG. 8 illustrates an exemplary message flow for prioritizing dataprovided to one device over data provided to another device according toone embodiment;

FIG. 9 is a block diagram of an exemplary network node according to oneembodiment; and

FIG. 10 is a block diagram of an exemplary MHD according to oneembodiment.

DETAILED DESCRIPTION

The embodiments set forth below represent the necessary information toenable those skilled in the art to practice the embodiments andillustrate the best mode of practicing the embodiments. Upon reading thefollowing description in light of the accompanying drawing figures,those skilled in the art will understand the concepts of the disclosureand will recognize applications of these concepts not particularlyaddressed herein. It should be understood that these concepts andapplications fall within the scope of the disclosure and theaccompanying claims.

The present disclosure discloses mechanisms for facilitating access to aservice provider network by integrating mobile subscriber devices intothe service provider network, and thereby extending the reach of theservice provider network to any location that a subscriber's device isenabled. In one embodiment, the subscriber's device, sometimes referredto herein as a mobile hotspot device (MHD), may be configured, orprovisioned, automatically by the service provider with a wireless localarea network (WLAN) having a predetermined name, such as a predeterminedservice set identifier (SSID). In one embodiment, the MHD periodicallybroadcasts the SSID to any other devices, sometimes referred to hereinas client devices, which may be in wireless range of the MHD. Certainclient devices may be programmed to detect the predetermined SSID, andin response, attempt to establish communication with the serviceprovider network via the MHD.

In another embodiment, rather than have an MHD broadcast its SSID, aclient device may be preconfigured with the SSIDs of one or more MHDs,and may periodically check to determine if it is within range of such anMHD by attempting to connect to such preconfigured SSIDs.

FIG. 1 is a block diagram illustrating a system 10 in which embodimentsof the present disclosure may be practiced. The system 10 includes aservice provider network 12 that includes a cellular network 14 and oneor more network nodes 16. The service provider network 12 is associatedwith a particular service provider, such as a wireless service provideror the like. The cellular network 14 comprises equipment associated withproviding cellular voice and data access to subscriber devices, such ascellular phones, and may comprise, for example, antennas, base stations,base station controllers and the like. The service provider network 12includes one or more network nodes 16 that comprise computing orprocessing devices, which, among other functionality that will bediscussed in greater detail herein, couples the service provider network12 with other networks, such as the Internet 18. While for purposes ofillustration, the network node 16 is depicted as being separate from thecellular network 14, the network node 16 may be a part of the cellularnetwork 14. Preferably, but not necessarily, the cellular network 14implements 4G or greater bandwidth through a technology such as WiMax orLTE.

The service provider network 12 may also include one or more WLANs 20placed at locations such as airports, coffee shops, shopping malls, andthe like, which offer access via the service provider network 12 to theInternet 18 to subscribers or transient users.

A mobile hotspot device (MHD) 22 includes a wireless cellular interface24 that establishes a wireless communications link 26 with the cellularnetwork 14. The wireless cellular interface 24 may comprise any suitablecircuitry and/or software necessary to facilitate the establishment ofthe wireless communications link 26. The wireless communications link 26is established in accordance with the conventional signaling andconnection mechanisms associated with the cellular network 14. The MHD22 comprises any portable, mobile computing or processing device capableof establishing the wireless communications link 26, such as a smartphone like an Apple® iPhone®, an Android®-based phone, or the like, alaptop computer that includes cellular data interface circuitry, acomputer tablet like the Apple® iPad®, Samsung Galaxy®, or the like, ora special purpose hotspot device, such as the Sprint® Overdrive® or thelike.

The MHD 22 also includes a WLAN interface 28 suitable for establishingone or more wireless WLAN communication links, such as Wi-Fi™communication links. The MHD 22 may also have one or more other wirelessinterfaces 30, such as a ZigBee wireless interface, a Bluetooth®wireless interface, and the like. A wireless router module 32 implementsa hotspot capability in the MHD 22. The wireless router module 32establishes a hotspot 34 via the WLAN interface 28 (or via the otherwireless interface 30) such that one or more client devices 36-1-36-N(generally, client devices 36) within the hotspot 34 may connect to theMHD 22 via corresponding wireless communication links 38-1-38-N(generally, wireless communication links 38). The precise boundaries ofthe hotspot 34 may vary based on any number of factors, includingobstructions, the particular wireless technology used, i.e., Wi-Fi,ZigBee, Bluetooth®, etc., interference from other RF emitters, and thelike. The wireless router module 32, as described in greater detailherein, routes requests for data from a client device 36 to the networknode 16, and routes data from the network node 16 that is destined forclient devices 36 to the appropriate client devices 36.

The client devices 36 comprise any computing or processing device thatincludes a wireless interface capable of establishing a wirelesscommunication link 38 with the MHD 22. For example, the client device36-1 may comprise a smart phone, such as an Apple® iPhone®, anAndroid®-based phone, or the like. The client device 36-2 may comprise alaptop computer. The client device 36-N may comprise a computer tabletlike the Apple® iPad®, Samsung® Galaxy®, or the like.

In one embodiment, the MHD 22 implements the hotspot 34 via a WLANhaving a predetermined service set identifier (SSID) that is associatedwith the service provider network 12. The MHD periodically beacons, orotherwise broadcasts, the SSID within the hotspot 34. A client device36, such as the client device 36-1, receives the beacon, and may beprogrammed or otherwise configured to recognize the predetermined SSID.The client device 36-1 then attempts to connect to the MHD 22 byestablishing a respective wireless communications link 38 with the MHD22. After establishing a wireless communications link 38 with the MHD22, the client device 36-1 may automatically provide the MHD 22credentials that identify the client device 36-1. The MHD 22 generatesan access request message that includes the credentials and communicatesthe credentials via the cellular network 14 to the network node 16. Thenetwork node 16 receives the access request message and authenticatesthe client device 36-1 as being authorized to access the serviceprovider network 12 based on the credentials. The network node 16indicates to the MHD 22 that the client device 36-1 is authorized toaccess the service provider network 12. Thereafter, with respect to theclient device 36-1, the MHD 22 serves primarily as a wireless routerthat facilitates communications between the client device 36-1 and theservice provider network 12. Via the service provider network 12, theclient device 36-1 may access other networks, such as a private networkor the Internet 18. Note that in one embodiment the exchange ofcommunications between the client device 36-1, the MHD 22, and thenetwork node 16 happens automatically upon the client device 36-1detecting the predetermined SSID. This eliminates the need for a user42-1 to enter usercodes, passwords, and the like. Merely by moving theclient device 36-1 within the hotspot 34 the user 42-1 may therebyobtain authenticated access to the Internet 18.

Providing such access to the client device 36-1 may be beneficial to theservice provider, an owner 40 of the MHD 22, and the users 42-1-42-N(generally users 42) of the client devices 36. In one embodiment,authorization to access the service provider network 12 may be based, atleast in part, on whether a user 42 has a subscription with the serviceprovider. Data consumed by a client device 36 may be counted against adata usage amount associated with the subscription of the respectiveuser 42. This benefits the service provider because it facilitatesselling more data to the respective user 42. The ability to access theInternet 18 by the user 42 from locations where the user 42 may nototherwise be able to access the Internet 18 benefits the user 42. Theowner 40 of the MHD 22 may also be compensated by the service providerin terms of an increased data usage amount associated with thesubscription of the owner 40, a reduced subscription fee, or in otherways.

FIG. 2 is a block diagram of the system 10 illustrated in FIG. 1 showinggreater details of some of the components. The network node 16 mayinclude a remote configuration module 44 that interfaces with aconfiguration module 46 in the MHD 22 to configure the MHD 22 to have awireless LAN with a predetermined SSID. Such configuration of the MHD 22may be automatically initiated, for example, after the owner 40indicates to the service provider that the owner 40 agrees to permit theMHD 22 to serve as a portal via which the client devices 36 can accessthe service provider network 12. This agreement may be indicated, forexample, by accepting the terms of a contract presented on the websiteof the service provider. The contract may include terms and provisionswhereby in return for allowing the MHD 22 to serve as a portal, theowner 40 will be compensated in one or more of the ways discussed above.Such acceptance may trigger the network node 16 to automaticallyconfigure the MHD 22 with the predetermined SSID. Such acceptance mayalso trigger additional software to be loaded onto the MHD 22 by thenetwork node 16 to implement the hotspot functionality, provide desiredaccounting or prioritization functionality for data destined to the MHD22 or the client devices 36, or any other desired or appropriateprocessing to carry out the functionality described herein.

In another embodiment, the owner 40 may configure the MHD 22 to have thewireless LAN with the predetermined SSID based on configurationinstructions provided by the service provider during the process ofaccepting the contract. In one embodiment, the service provider mayremotely manage the wireless LAN with the predetermined SSID in the MHD22, including, for example, managing an encryption type, trafficpolicing, rate shaping, implementing a quality of service (QOS) policy,remote monitoring, and the like. Remote management may include limitingthe number of connections of client devices 36 to the MHD 22. Suchremote management may be implemented by any suitable means, including,for example, one or more of SNMP, OMA-DM, TR69, XML, and the like. Thenetwork node may also implement a user interface for a service provideroperator to remotely manage the MHD 22.

In one embodiment, the network node 16 also includes an authenticationmodule 48 used to authenticate the client device 36 in response to anaccess request message received from the MHD 22. Such authenticationmodule 48 may access information, such as configuration data 50, todetermine whether the credentials included in the access request messageidentify a known user 42. A rate limiting, policing and prioritizationmodule 52 may, in accordance with rules or criteria identified in theconfiguration data 50 or received from the MHD 22, limit the rate ofcertain data flows to the MHD 22 and/or prioritize such data flows. Forexample, one user 42 may, based on a particular subscription, enjoy a 3mega-bit per second (mbps) data rate, and another a 1 mbps data rate.Alternately, after a user 42 exceeds the data usage allotment, orthreshold, associated with their subscription, additional data may beprovided at an increased cost, and/or at a reduced data rate. The MHD 22may also be able to identify certain client devices 36, such as familymembers' client devices 36, as having a higher priority, or faster datarates, than any other client devices 36. In another embodiment, the MHD22 may implement the rate, policing and prioritization functiondiscussed herein in a rate limiting, policing and prioritization module54 contained in the MHD 22.

A billing module 56 in the network node 16 may, among other features,maintain data usage by various client devices 36 and the MHD 22, andcut-off, or de-authorize, client devices 36 that exceed predetermineddata usage allotments associated with respective subscriptions, orensure that data used in excess of such predetermined data usageallotments are charged at higher incremental rates. The billing module56 may also allocate certain data usage by client devices 36 to the MHD22, such as those client devices 36 that are associated with the samesubscription as the MHD 22. The billing module 56 may also maintaininformation suitable for compensating the owner 40 for allowing the MHD22 to be used as a portal to the service provider network 12.

The wireless router module 32 may maintain data that identifies one ormore wireless local area networks that are implemented by the MHD 22.For example, network configuration data 58 may identify a personal Wi-Finetwork that has a private SSID that the owner 40 provides to only closefriends and family members. Network configuration data 60 may define theWi-Fi network automatically configured by the remote configurationmodule 44 that offers a portal to the service provider network 12 forany client devices 36 that detect and identify the predetermined SSID.The network configuration data 60 may be configured with any suitableparameters or attributes associated with a wireless LAN.

SSIDs may also be used by the rate limiting, policing and prioritizationmodule 52 or the rate limiting, policing and prioritization module 54 asthe basis for rate limiting and/or prioritization. For example, devicescommunicatively coupled to the MHD 22 via the private SSID may enjoyhigher data rates and/or priority than those communicatively coupled tothe predetermined SSID.

In one embodiment, the MHD 22 may also contain configuration data 62that includes, among other information, a permitted client devices list64. The permitted client devices list 64 may identify client devices 36that are permitted by the MHD 22 to access the service provider network12. Thus, upon receiving a request from a client device 36 to connect tothe MHD 22, the MHD 22 may first verify that the client device 36 isidentified on the permitted client devices list 64, and if not, refuseto allow the client device 36 to connect to the MHD 22.

The client devices 36 may contain a client application 66 provided bythe service provider network 12 that is programmed to detect andidentify the predetermined SSID beaconed or otherwise broadcast by anMHD, such as the MHD 22. The predetermined SSID may not be identicalacross each MHD 22, and the phrase “predetermined SSID” encompasses anynaming convention that would permit a client device 36 to detect andidentify the SSID as potentially being associated with the serviceprovider. For example, a first portion of the SSID may be generic acrossall MHDs 22, and a second portion of the SSID may be unique to aparticular MHD 22. The client application 66 may parse each availableSSID and upon determining that an SSID contains the first genericportion associated with the service provider network 12, attempt toconnect to the service provider network 12. The client application 66may be downloaded from a website offered by the service provider, or maybe a part of the initial software package provided on the client device36 when purchased from the service provider. In another embodiment, theclient device 36 may be preconfigured with the SSID of the MHD 22, andmay periodically check to determine if it is within range of the MHD 22by attempting to connect to the MHD 22 via such preconfigured SSID.

FIG. 3 illustrates an exemplary message flow for facilitating access tothe service provider network 12 by a client device 36 via the MHD 22.FIG. 3 will be discussed in conjunction with FIG. 2. Initially, assumethat the network node 16 initiates a configuration sequence with the MHD22 to generate a wireless local area network having a predetermined SSID(FIG. 3, step 1000). The MHD 22 generates the network and acknowledgesthis to the network node 16 (FIG. 3, steps 1002-1004). The MHD 22enables the network and thereby offers the hotspot 34 (FIG. 3, step1006).

The client device 36-1 receives the beacon identifying the hotspot withthe predetermined SSID. The client device 36-1 identifies the hotspot ashaving the predetermined SSID (FIG. 3, step 1008). Because the clientdevice 36-1 recognizes the hotspot 34 as one associated with the serviceprovider network 12, the client device 36-1 establishes a wirelesscommunication link 38-1 with the MHD 22, and provides the MHD 22credentials for authentication with the service provider network 12(FIG. 3, step 1010). If the MHD 22 maintains a permitted client deviceslist 64, the MHD 22 accesses the permitted client devices list 64 todetermine whether the client device 36-1 is identified as a permitteddevice (FIG. 3, step 1012). The MHD 22 then generates and sends anaccess request message that includes the credentials provided by theclient device 36-1 to the network node 16 (FIG. 3, step 1014). Thenetwork node 16 determines that the client device 36-1 is authorized toaccess the service provider network 12 based on the credentials (FIG. 3,step 1016). The network node 16 indicates to the MHD 22 that the clientdevice 36-1 is authenticated, and therefore authorized to access theservice provider network 12 through the MHD 22 (FIG. 3, step 1018). TheMHD 22 notifies the client device 36-1 that the client device 36-1 isauthorized to access the service provider network 12 (FIG. 3, step1020).

In one embodiment, at some point during the authentication process, thenetwork node 16 may communicate a message to the MHD 22 indicating thatthe client device 36-1 seeks to access the service provider network 12through the MHD 22. The MHD 22 may present this to the owner 40, alongwith options, such as Allow or Reject. If the owner 40 selects theReject option, the MHD 22 informs the network node 16 that the requesthas been denied and the network node 16 rejects the access requestmessage. If the owner 40 selects the Allow selection, the network node16 indicates to the MHD 22 that the client device 36-1 is now permittedto access the service provider network 12. In another embodiment, priorto even sending the access request message to the network node 16, theMHD 22 may identify the client device 36-1 and provide the owner 40 anAllow or Reject option upon receiving the credentials from the clientdevice 36-1

FIG. 4 is a block diagram of the system illustrated in FIG. 1 accordingto another embodiment. In this embodiment the MHD 22 detects thepresence of the WLAN network 20. The owner 40 or the MHD 22 determinesthat the WLAN network 20 is associated with the service provider network12 and that the service provider network 12 is therefore accessible. TheMHD 22 establishes a wireless communications link 68 with the WLANnetwork 20, and communicates with the network node 16 as discussedpreviously, except through the WLAN network 20 instead of the cellularnetwork 14. Whether the MHD 22 is connected via the WLAN network 20 orthe cellular network 14 may be transparent to any client devices 36 thatconnect to the service provider network 12 via the MHD 22. The MHD 22may select the WLAN network 20 over the cellular network 14 based oncertain criteria, such as a bandwidth of the WLAN network 20 compared tothat of the cellular network 14, or may select the WLAN network 20because of financial criteria, such as the service provider may notcharge the MHD 22 for data usage via the WLAN network 20, or may chargeat a reduced rate with respect to the cellular network 14.

FIG. 5 illustrates an exemplary message flow for providing voice signalsand data destined for different devices to the MHD 22 concurrently.Assume that the service provider network 12 has authenticated the clientdevice 36-1 to access the service provider network 12 via the MHD 22.Assume further that the MHD 22 is coupled to the service providernetwork 12 via the wireless communications link 26 with the cellularnetwork 14. The owner of the MHD 22 is participating in a voice callwith another party. Concurrently with the voice call, the client device36-1 seeks data such as a web page or video from the Internet 18. Thenetwork node 16 thus concurrently provides voice signals from the otherparty to whom the owner 40 is speaking and data destined for the clientdevice 36-1 to the MHD 22 (FIG. 5, step 2000). The MHD 22 renders thevoice signals to the owner 40, such as via a speaker contained in theMHD 22 (FIG. 5, step 2002). The MHD 22 also substantially concurrentlyprovides the data that is destined for the client device 36-1 to theclient device 36-1. Thus, in the case where the MHD 22 comprises a smartphone, for example, the owner 40 may enjoy cellular voice capabilitieswhile the MHD 22 concurrently serves as a portal to the service providernetwork 12 for the client device 36-1.

FIG. 6 illustrates an exemplary message flow for accounting for datausage by devices that receive data via the service provider network 12according to one embodiment. In this embodiment the owner 40 uses theMHD 22 to access the Internet 18 at substantially the same time the user42-1 uses the client device 36-1 to access the Internet 18. The MHD 22generates a request for data X and sends the request to the network node16 for communication to the Internet 18 (FIG. 6, step 3000). The clientdevice 36-1 substantially concurrently generates a request for data Yand sends the request via the MHD 22 to the network node 16 forcommunication to the Internet 18 (FIG. 6, steps 3002-3004). The networknode 16 receives the requested data from the Internet 18 and providesdata X and Y to the MHD 22 (FIG. 6, step 3006). The MHD 22 consumes dataX, i.e., presents data X to the owner 40 or otherwise processes data Xin accordance with the purposes of requesting data X, and provides dataY, which is destined for the client device 36-1, to the client device36-1 (FIG. 6, steps 3008-3010).

The network node 16 maintains data usage quantifiers, such as counters,for both the MHD 22 and the client device 36-1 in order to monitor theircumulative data usage in accordance with their respective subscriptionswith the service provider. Thus, the network node 16 increases the datausage quantifier of the MHD 22 by the amount of data X (FIG. 6, step3012). The network node 16 also increases the data usage quantifier ofthe client device 36-1 by the amount of data Y (FIG. 6, step 3014). Thenetwork node 16 determines that the data usage quantifier associatedwith the client device 36-1 now exceeds the monthly allotment for theclient device 36-1 based on the subscription via which the client device36-1 obtains access to the service provider network 12 (FIG. 6, step3016). The network node 16 sends a message to the MHD 22 de-authorizingaccess to the service provider network 12 by the client device 36-1(FIG. 6, step 3018). The MHD 22 disconnects the client device 36-1 toprevent further access to the service provider network 12 (FIG. 6, step3020). The MHD 22 may also provide information to the client device 36-1for display to the user 42-1 explaining the reason the client device36-1 has been disconnected.

It will be apparent that de-authorizing the client device 36-1 is onlyone of several different actions that network node 16 may take upondetermining that the data usage quantifier associated with the clientdevice 36-1 exceeds the monthly allotment. For example, the network node16 may simply continue to allow the client device 36-1 to access theservice provider network 12 even though the data usage exceeds themonthly allotment because the user 42-1 may be charged for such data ata higher rate than for data under the monthly allotment. The networknode 16 may also prioritize data differently based on whether the clientdevice 36 for which the data is destined has exceeded the monthly datausage allotment. In particular, the network node 16 may prioritize datarequests from such client devices 36 at a lower priority than datarequests from client devices 36 that have not exceeded their monthlydata allotments.

In another embodiment, the MHD 22 may track data usage of client devices36, and provide various actions based on the data usage quantifierassociated with a client device 36. For example, if the MHD 22determines that a particular client device 36 is accessing asignificantly higher quantity of data than other client devices 36, theMHD 22 may prioritize other client devices 36 over such client device36. The MHD 22 may also receive, from the network node 16, the datausage quantifiers associated with the client devices 36, tally the dataconsumed by the client devices 36, and disconnect or otherwisede-authorize client devices 36 that have exceeded a monthly allotmentassociated with the respective subscription. Upon disconnect of a clientdevice 36, either voluntarily or involuntarily, the MHD 22 may providethe updated data usage quantifier to the network node 16 for billing andaccounting purposes.

FIG. 7 illustrates another exemplary message flow for accounting fordata usage by devices that receive data via the service provider network12 according to another embodiment. In this embodiment the client device36-2 is associated with the subscription of the MHD 22. For example, theclient device 36-2 may be identified in the subscription as one ofseveral client devices 36 that are permitted to access the serviceprovider network 12 pursuant to the subscription. The client device 36-2generates a request for data X and sends the request via the MHD 22 tothe network node 16 for communication to the Internet 18 (FIG. 7, steps4000-4002). The network node 16 receives data X from the Internet 18 anddetermines that the client device 36-2 is associated with thesubscription of the MHD 22 (FIG. 7, step 4004). The network node 16 thenadjusts the data usage quantifier associated with the MHD 22 by thequantity of data X (FIG. 7, step 4006). The network node provides data Xto the MHD 22 for communication to the client device 36-2 (FIG. 7, steps4008-4010).

FIG. 8 illustrates an exemplary message flow for prioritizing datadestined for one device over data destined for another device accordingto one embodiment. Assume that the owner 40 requests data X, whichcomprises a first movie stream, from the Internet 18. The network node16 receives the request from the MHD 22 for data X, and begins providingthe first movie stream to the MHD 22 for presentation to the owner 40(FIG. 8, steps 5000-5002). The user 42-1, while the movie is beingstreamed to the MHD 22, then requests data Y, which comprises a secondmovie stream. The client device 36-1 generates a request for data Y andsends it to the network node 16 via the MHD 22 (FIG. 8, steps5004-5006). The network node 16 receives the request for data Y, andrecognizes that data X is destined for the MHD 22, while data Y isdestined for the client device 36-1, which is a device other than theMHD 22. The network node 16 prioritizes the data X stream over the dataY stream (FIG. 8, step 5008). Such prioritization can take any ofseveral different forms. In the case of streams of data, such as a moviestream, the network node 16 may allocate a larger bandwidth to the MHD22 than to the client device 36-1. The reduced bandwidth available tothe client device 36-1 may result in a lower resolution movie beingprovided to the client device 36-1, or may cause less fluid playback ofthe movie than that enjoyed by the owner 40. The network node 16 thenprovides the data X and Y to the MHD 22 and client device 36-1,respectively, in accordance with the priority (FIG. 8, steps 5010-5012).

Prioritization may be configured by the owner 40 such that certainclient devices 36, such as those associated with the subscription viawhich the MHD 22 accesses the service provider network 12, have higherpriority than any other client devices 36. The owner 40 may indicatethat the MHD 22 enjoys a highest priority in any situation.Alternatively, prioritization may be determined by the service providerand may be based on subscription level, subscription status, type ofdata being requested, or any other criteria.

In one embodiment, the MHD 22 may be able to provide location servicesfor a client device 36 that cannot otherwise provide a location. Forexample, the MHD 22 may include a GPS receiver that allows the MHD 22 toidentify its current location on the earth. If the MHD 22 is connectedto a client device 36 via a wireless communication link 38, then theclient device 36 is likely within several hundred feet of the MHD 22. Ifthe wireless communication link 38 comprises a Bluetooth® or ZigBeewireless communications link 38, then the client device is likely evencloser to the MHD 22. If requested, the MHD 22 may be able to report itsown location as the location of the client device 36 and while notexact, may suffice for an emergency situation.

In one embodiment, one MHD 22 may initiate a handoff of a client device36 to another MHD 22, or to a cellular base station, picocell,femtocell, or the like based on, for example, metrics related to signalperformance (e.g., signal strength, throughput capability, latency,congestion), cost (e.g., cost of building and maintaining capacity onthe network to which the client device 36 would be transferred), userinput (e.g., the owner 40 of the MHD 22 may select to have the clientdevice 36 transfer to another network, or the user 42 of the clientdevice 36 may select to be transferred to another network based onpre-set or dynamically chosen selection criteria), battery liferemaining on the MHD 22, or location of the MHD 22 or the client device36, for example. The handoff may be initiated by the MHD 22 or by theclient device 36.

FIG. 9 is a block diagram of a network node 16 according to oneembodiment. As discussed previously, the functionality attributed to thenetwork node 16 may be performed by a single processing or computingdevice, or may be performed by multiple such devices maintained by theservice provider. The exemplary network node 16 illustrated in FIG. 9may comprise a workstation, a telecommunications switch, or the like.The network node 16 includes a processor 100, a system memory 102, and asystem bus 104. The system bus 104 provides an interface for systemcomponents including, but not limited to, the system memory 102 and theprocessor 100. The processor 100 can be any of various commerciallyavailable or proprietary processors. Dual microprocessors and othermulti-processor architectures may also be employed as the processor 100.

The system bus 104 may be any of several types of bus structures thatmay further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and/or a local bus using any of a varietyof commercially available bus architectures. The system memory 102 mayinclude non-volatile memory 106 (e.g., read only memory (ROM), erasableprogrammable read only memory (EPROM), electrically erasableprogrammable read only memory (EEPROM), etc.), and/or volatile memory108 (e.g., random access memory (RAM)). A basic input/output system(BIOS) 110 may be stored in the non-volatile memory 106, and can includethe basic routines that help to transfer information between elementswithin the network node 16. The volatile memory 108 may also include ahigh-speed RAM such as static RAM for caching data.

The network node 16 may further include the computer-readable storage112, which may comprise, for example, an internal hard disk drive (HDD)(e.g., enhanced integrated drive electronics (EIDE) or serial advancedtechnology attachment (SATA)) HDD (e.g., EIDE or SATA) for storage,flash memory, or the like. The storage 112 may store, for example, theconfiguration data 50, data usage quantifiers, and the like. The drivesand associated computer-readable and computer-usable media providenon-volatile storage of data, data structures, computer-executableinstructions, and so forth. Although the description ofcomputer-readable media above refers to an HDD, it should be appreciatedby those skilled in the art that other types of media which are readableby a computer, such as Zip disks, magnetic cassettes, flash memorycards, cartridges, and the like, may also be used in the exemplaryoperating environment, and further, that any such media may containcomputer-executable instructions for performing novel methods of thedisclosed architecture.

A number of program modules can be stored in the storage 112 and in thevolatile memory 108, including an operating system 114 and one or moreprogram modules 116, which may implement the functionality describedherein in whole or in part, including, for example, functionalityassociated with the remote configuration module 44, the authenticationmodule 48, the billing module 56, the rate limiting, policing, andprioritization module 52, and other processing and functionalitydescribed herein. It is to be appreciated that the embodiments can beimplemented with various commercially available operating systems 114 orcombinations of operating systems 114.

All or a portion of the embodiments may be implemented as a computerprogram product stored on a transitory or non-transitory computer-usableor computer-readable medium, such as the storage 112, which includescomplex programming instructions, such as complex computer-readableprogram code, configured to cause the processor 100 to carry out thesteps described herein. Thus, the computer-readable program code cancomprise software instructions for implementing the functionality of theembodiments described herein when executed on the processor 100. Theprocessor 100, in conjunction with the program modules 116 in thevolatile memory 108, may serve as a control system for the network node16 that is configured to, or adapted to, implement the functionalitydescribed herein.

An administrator may be able to enter commands and information into thenetwork node 16 through one or more input devices, such as, for example,a keyboard (not illustrated); a pointing device, such as a mouse (notillustrated); or a touch-sensitive surface. Other input devices mayinclude a microphone, an infrared (IR) remote control, a joystick, agame pad, a stylus pen, or the like. These and other input devices maybe connected to the processor 100 through an input device interface 118that is coupled to the system bus 104, but can be connected by otherinterfaces such as a parallel port, an IEEE 1394 serial port, aUniversal Serial Bus (USB) port, an IR interface, etc.

The network node 16 may also include one or more communicationinterfaces 120 for communicating with, for example, various networks,including the cellular network 14 and the WLAN network 20 discussedherein. The one or more communication interfaces 120 may comprise, forexample, wired or wireless network interfaces. The network node 16 mayalso include a video port 122 that interfaces with a display 124 thatprovides information to the administrator.

FIG. 10 is a block diagram of the MHD 22 according to one embodiment.The exemplary MHD 22 illustrated in FIG. 10 may comprise any portable,mobile computing or processing device capable of establishing a wirelesscommunications link, such as a smart phone like an Apple® iPhone®, anAndroid®-based phone, or the like, a laptop computer that includescellular data interface circuitry, a computer tablet like the Apple®iPad®, Samsung Galaxy®, or the like, or a special purpose hotspotdevice, such as the Sprint® Overdrive® or the like. The MHD 22 includesa processor 130, a system memory 132, and a system bus 134. The systembus 134 provides an interface for system components including, but notlimited to, the system memory 132 and the processor 130. The processor130 can be any of various commercially available or proprietaryprocessors. Dual microprocessors and other multi-processor architecturesmay also be employed as the processor 130.

The system bus 134 may be any of several types of bus structures thatmay further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and/or a local bus using any of a varietyof commercially available bus architectures. The system memory 132 mayinclude non-volatile memory 136 (e.g., read only memory (ROM), erasableprogrammable read only memory (EPROM), electrically erasableprogrammable read only memory (EEPROM), etc.) and/or volatile memory 138(e.g., random access memory (RAM)). A basic input/output system (BIOS)140 may be stored in the non-volatile memory 136, and can include thebasic routines that help to transfer information between elements withinthe MHD 22. The volatile memory 138 may also include a high-speed RAMsuch as static RAM for caching data.

The MHD 22 may further include the computer-readable storage 142, whichmay comprise, for example, an internal hard disk drive (HDD) (e.g.,enhanced integrated drive electronics (EIDE) or serial advancedtechnology attachment (SATA)) HDD (e.g., EIDE or SATA) for storage,flash memory, or the like. The storage 142 may store, for example, theconfiguration data 62, network configuration data 58, 60, and the like.The drives and associated computer-readable and computer-usable mediaprovide non-volatile storage of data, data structures,computer-executable instructions, and so forth. Although the descriptionof computer-readable media above refers to an HDD, it should beappreciated by those skilled in the art that other types of media whichare readable by a computer, such as Zip disks, magnetic cassettes, flashmemory cards, cartridges, and the like, may also be used in theexemplary operating environment, and further, that any such media maycontain computer-executable instructions for performing novel methods ofthe disclosed architecture.

A number of program modules can be stored in the storage 142 and in thevolatile memory 138, including an operating system 144 and one or moreprogram modules 146, which may implement the functionality describedherein in whole or in part, including, for example, functionalityassociated with the configuration module 46, the wireless router module32, and other processing and functionality described herein. It is to beappreciated that the embodiments can be implemented with variouscommercially available operating systems 144 or combinations ofoperating systems 144.

All or a portion of the embodiments may be implemented as a computerprogram product stored on a transitory or non-transitory computer-usableor computer-readable medium, such as the storage 142, which includescomplex programming instructions, such as complex computer-readableprogram code, configured to cause the processor 130 to carry out thesteps described herein. Thus, the computer-readable program code cancomprise software instructions for implementing the functionality of theembodiments described herein when executed on the processor 130. Theprocessor 130, in conjunction with the program modules 146 in thevolatile memory 138, may serve as a control system for the MHD 22 thatis configured to, or adapted to, implement the functionality describedherein.

A user, such as the owner 40, may be able to enter commands andinformation into the MHD 22 through one or more input devices, such as,for example, a keyboard (not illustrated); a pointing device, such as amouse (not illustrated); or a touch-sensitive surface. Other inputdevices may include a microphone, an infrared (IR) remote control, ajoystick, a game pad, a stylus pen, or the like. These and other inputdevices may be connected to the processor 130 through an input deviceinterface 148 that is coupled to the system bus 134, but can beconnected by other interfaces such as a parallel port, an IEEE 1394serial port, a Universal Serial Bus (USB) port, an IR interface, etc.

The MHD 22 may also include the wireless cellular interface 24 suitablefor establishing a wireless communications link 26 with a cellularnetwork, such as the cellular network 14. The MHD 22 may include theWLAN interface 28 suitable for establishing a wireless communicationslink 68 with a WLAN network, such as the WLAN network 20. The MHD 22 mayinclude one or more other wireless interfaces 30 suitable forestablishing other wireless communications links, such as ZigBeewireless communications links and Bluetooth® wireless communicationslinks. The MHD 22 may also include video circuitry 150 that interfaceswith a display 152 that provides information to the owner 40.

Those skilled in the art will recognize improvements and modificationsto the preferred embodiments of the present disclosure. All suchimprovements and modifications are considered within the scope of theconcepts disclosed herein and the claims that follow.

What is claimed is:
 1. A method for providing access to a serviceprovider network associated with a service provider and comprising atleast one network node, comprising: establishing, by the at least onenetwork node, a first wireless communication link with a mobile hotspotdevice, the mobile hotspot device configured to establish a secondwireless communication link with at least one client device; receiving,by the network node, an access request message from the mobile hotspotdevice, the access request message comprising credentials provided bythe at least one client device; determining, by the network node, thatthe at least one client device is authorized to access the serviceprovider network through the mobile hotspot device based on thecredentials; indicating to the mobile hotspot device that the at leastone client device is authorized to access the service provider networkthrough the mobile hotspot device; receiving, by the network node, afirst request for first data destined for the at least one clientdevice; prior to delivering the first data receiving a second requestfor second data destined for the mobile hotspot device; prioritizing thesecond request over the first request based on a destination of thesecond data; and delivering the second data to the mobile hotspot deviceprior to delivering the first data to the at least one client device. 2.The method of claim 1, wherein the mobile hotspot device comprises acellular phone of a subscriber of the service provider.
 3. The method ofclaim 1, further comprising: provisioning, by the network node, themobile hotspot device with a wireless network having a predeterminedSSID; and wherein the at least one client device seeks access to themobile hotspot device in response to detecting the predetermined SSID.4. The method of claim 1, further comprising: providing a first quantityof data to the mobile hotspot device destined for a device other thanthe at least one client device; providing a second quantity of data tothe mobile hotspot device destined for the at least one client device;maintaining a first data usage quantifier that tracks a first cumulativequantity of data provided to the device other than the at least oneclient device pursuant to a subscription associated with the mobilehotspot device; maintaining a second data usage quantifier that tracks asecond cumulative quantity of data provided to the at least one clientdevice pursuant to a subscription associated with the at least oneclient device; increasing the first data usage quantifier based on thefirst quantity of data but not based on the second quantity of data; andincreasing the second data usage quantifier based on the second quantityof data.
 5. The method of claim 4, wherein the device other than the atleast one client device comprises the mobile hotspot device.
 6. Themethod of claim 4, wherein the device other than the at least one clientdevice comprises a second client device, the second client device beingassociated with the subscription associated with the mobile hotspotdevice.
 7. The method of claim 4, further comprising: making adetermination that the second data usage quantifier exceeds apredetermined threshold; and based on the determination, de-authorizingaccess to the service provider network by the at least one clientdevice.
 8. The method of claim 1, wherein determining, by the networknode, that the at least one client device is authorized to access theservice provider network through the mobile hotspot device based on thecredentials comprises determining that the credentials identify asubscriber of the service provider.
 9. The method of claim 1, furthercomprising: providing a message to the hotspot device for presentationto a user of the hotspot device that the at least one client device hasrequested access to the service provider network through the mobilehotspot device.
 10. A mobile hotspot device, comprising: at least onewireless interface configured to establish first and second wirelesscommunication links; a processor coupled to the at least one wirelessinterface and configured to: communicate with a service provider networkvia the first wireless communication link; communicate with a clientdevice via the second wireless communication link; receive a requestfrom the client device to access the service provider network; submitthe request, including credentials associated with the client device, tothe service provider network; receive authorization from the serviceprovider network that the client device is authorized to access theservice provider network; and receive a first request for first datafrom the client device; receive a second request for second data from auser of the mobile hotspot device; prioritize the second request overthe first request based on a destination of the second data; and deliverthe second data to the user of the mobile hotspot device prior todelivering the first data to the at least one client device.
 11. Themobile hotspot device of claim 10, wherein the processor is furtherconfigured to: route a plurality of requests for data received from theclient device to the service provider network; and route a plurality ofresponses to the requests for data to the client device.
 12. The mobilehotspot device of claim 10, wherein the processor is further configuredto: prior to submitting the request to access the service providernetwork, access configuration data identifying permitted client devices;and determine that the client device is identified as a permitted clientdevice.
 13. The mobile hotspot device of claim 10, wherein the at leastone wireless interface comprises a first wireless interface and a secondwireless interface, the first wireless interface comprising a cellularwireless interface and establishing the first wireless communicationlink, and the second wireless interface comprising a WLAN wirelessinterface and establishing the second wireless communication link. 14.The mobile hotspot device of claim 10, wherein the at least one wirelessinterface comprises a first wireless interface and a second wirelessinterface, the first wireless interface comprising a cellular wirelessinterface and establishing the first wireless communication link, andthe second wireless interface comprising one of a Bluetooth® wirelessinterface and a ZigBee wireless interface, and establishing the secondwireless communication link.
 15. The mobile hotspot device of claim 10,wherein the at least one wireless interface comprises a first wirelessinterface and a second wireless interface, the first wireless interfacecomprising a cellular wireless interface and the second wirelessinterface comprising a WLAN wireless interface, the processor furtherconfigured to: detect that the service provider network is accessiblevia both the first wireless interface and the second wireless interface;and select one of the first wireless interface and the second wirelessinterface to establish the first wireless communication link based on atleast one criterion.
 16. The mobile hotspot device of claim 15, whereinthe at least one criterion comprises a bandwidth of the first wirelessinterface compared to a bandwidth of the second wireless interface. 17.The mobile hotspot device of claim 10, wherein the processor is furtherconfigured to: access a predetermined data usage threshold associatedwith the client device; make a determination that a quantity of datadelivered to the client device via the mobile hotspot device hasexceeded the predetermined data usage threshold; and in response to thedetermination de-authorize access to the service provider network by theclient device.
 18. The method of claim 1, further comprising providing avoice signal destined for the mobile hotspot device to the mobilehotspot device via the first wireless communication link whileconcurrently providing data destined for the at least one client deviceto the mobile hotspot device via the first wireless communication link.